home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
tsql
/
doc
/
tsql.mail
/
000075_UZTBB@CUNYVM.CUNY.EDU _Thu Apr 8 12:57:42 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1996-01-31
|
1KB
Received: from Arizona.edu (Hopey.Telcom.Arizona.EDU) by optima.cs.arizona.edu (5.65c/15) via SMTP
id AA05736; Thu, 8 Apr 1993 10:13:11 MST
Received: from CUNYVM.CUNY.EDU (MAILER@CUNYVMV2) by Arizona.edu (PMDF #2381 )
id <01GWRJO6F4Z491WOSJ@Arizona.edu>; Thu, 8 Apr 1993 10:12:44 MST
Received: from CUNYVM.CUNY.EDU (NJE origin UZTBB@CUNYVM) by CUNYVM.CUNY.EDU
(LMail V1.1d/1.7f) with RFC822 id 3506; Thu, 8 Apr 1993 13:11:12 -0400
Date: 08 Apr 1993 12:57:42 -0400 (EDT)
From: UZTBB@CUNYVM.BITNET
Subject: more on the benchmark
To: tsql@cs.arizona.edu
Message-Id: <01GWRJOGQH1291WOSJ@Arizona.edu>
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Rick points out that dept is a time varying attribute. The reason for
considering an attribute like budget is it is not a non-key attrinute.
It can be compared with another non-key attribute like salary. Dept
is a key in mgr relation.
I agree with Jim renameing the mgr relation as departmet.
I also agree with Jim on his coorect observation on the keys. I guess
name can be replaced by ss#. However, this is not as appealing as the
name is. We should be aware of implications of assuming name as a key.
I still feel strongly that we should not look for 3Nf relations.
How does TSQL community feel about this?
Abdullah